package Data::Conveyor::App::Mutex;

use strict;
use warnings;
use Error::Hierarchy::Util 'assert_defined';
use Data::Conveyor::Mutex;


our $VERSION = '0.02';


use base 'Class::Scaffold::App::CommandLine';


# define the 'mutex' accessor via 'get_set_std', not via 'object =>
# Data::Conveyor::Mutex', because we don't always have a mutex object,
# depending on the environment. In DESTROY() we do 'return unless
# $self->mutex', which would still trigger the mutex object constructor - so
# we avoid that.

__PACKAGE__
    ->mk_scalar_accessors(qw(mutex_key))
    ->mk_framework_object_accessors(mutex => 'mutex');


sub app_init {
    my $self = shift;
    $self->SUPER::app_init(@_);

    if ($self->delegate->respect_mutex) {

        assert_defined $self->mutex_key, 'called without set mutex_key.';
        $self->mutex->application($self->mutex_key);
        $self->mutex->mutex_getconf;

        exit 0 unless $self->mutex->get_mutex;
    }
}


DESTROY {
    my $self = shift;
    return unless $self->delegate->respect_mutex && $self->mutex;
    $self->mutex->release_mutex;
}


1;


__END__

{% USE p = PodGenerated %}

=head1 NAME

{% p.package %} - stage-based conveyor-belt-like ticket handling system

=head1 SYNOPSIS

    {% p.package %}->new;

=head1 DESCRIPTION

None yet. This is an early release; fully functional, but undocumented. The
next release will have more documentation.

=head1 METHODS

=over 4

{% p.write_methods %}

=back

{% p.write_inheritance %}

{% PROCESS standard_pod %}

=cut

